Multi-signature verification network

ABSTRACT

Systems and methods for authorizing a blockchain transaction. A verification network receives a transaction request for the blockchain transaction from a payer device including a first signature generated by a first private key associated with a payer. The verification network broadcasts a verification request to verification system(s) which assess pre-agreed threshold parameters. If the parameter(s) are satisfied, at least one verification system perfects the transaction by generating a second signature using a second private key, and broadcasts the transaction to the blockchain network. If the parameter(s) are not satisfied, verification offer(s) from among the verification system(s) including the second signature(s) are used to prompt the payer device to confirm the blockchain transaction by selecting at least one of the offer(s). The verification network receives selected offer(s) from the payer device and broadcasts the transaction to the blockchain network, in accordance with the selected offer(s) and the transaction request.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 17/400,236, filed Aug. 12, 2021 know U.S. Pat. No. 11,386,423), which is a continuation of U.S. application Ser. No. 17/226,142, filed Apr. 9, 2021 (now U.S. Pat. No. 11,120,435), which is a continuation of U.S. application Ser. No. 17/003,044, filed Aug. 26, 2020 (now U.S. Pat. No. 11,004,068), which is a continuation of U.S. application Ser. No. 16/808,127, filed Mar. 3, 2020 (now U.S. Pat. No. 10,922,685), which is a continuation of U.S. application Ser. No. 16/561,295, filed Sep. 5, 2019 (now U.S. Pat. No. 10,621,579), which claims priority from U.S. Provisional Application No. 62/727,824, filed Sep. 6, 2018.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to systems and methods for authorizing blockchain-based transactions of digital assets, and more specifically, to a multi-signature authorization system including a multi-signature verification network that leverages a pool of trusted verification institutions to generate at least one signature and at least one verification offer together with a payer signature, in order to authorize blockchain-based transactions.

BACKGROUND

The use of blockchain technology for transactions involving digital assets such as cryptocurrencies has become increasingly popular due to the decentralized nature of transactions, the use of a mathematically verifiable ledger, near-immediate settlement, and isolation from operational, technical, or geo-political concentration risks. Although blockchain technology presents these advantages, managing cryptographic keys is burdensome and dangerous, exposing users to the dual threats of electronic theft and accidental loss of assets. Further, with near-immediate settlement comes a lack of “claw-back” reversibility of transactions, increasing the impact of fraud. Accordingly, there is a need to provide the security, safety, and reversibility of traditional centralized payment systems without reinstating concentration risks posed by relying on any single service provider.

SUMMARY

Aspects of the present disclosure relate to systems, methods and non-transitory computer readable media for authorizing a blockchain transaction. In some examples, system may include a verification network in communication with at least a payer computing device associated with a payer, a verification pool that includes one or more independent third-party verification computing systems (e.g., verification providers or verification institutions), and a blockchain network. In some examples, the verification network includes a computing system having a processor and a memory having programming instructions stored thereon, where the programming instructions, when executed by the processor, cause the system to perform an operation for authorizing the blockchain transaction. The operation of the verification network includes receiving, from the payer computing device, a partially-signed blockchain transaction (e.g., a transaction request). The transaction may include a first signature, where the first signature may be generated by a first private key created and managed by the payer (e.g., a first private key associated with the payer). In one example, the first signature may be the only signature included in the (partially-signed) transaction. In some examples, the partially-signed transaction may be enriched by the verification network with situational details such as (without being limited to) time, value, geolocation, merchant statistics and/or any suitable information that may be useful to a verification provider in analyzing the likelihood of attempted fraud. Since, in an exemplary embodiment, the payer private key must be protected by the payer, the nature of the present disclosure significantly mitigates the impact of unauthorized access to this payer private key, thereby significantly increasing the attractiveness of existing backup solutions.

The operation of the verification network further includes broadcasting the partially-signed transaction and details relating to one or more pre-agreed threshold parameters (e.g., risk assessment details) to the one or more verification providers. The operation may further include assessing, by at least one verification provider from among the verification pool, the one or more pre-agreed threshold parameters associated with the partially-signed transaction. The assessing may be a part of a broader risk analysis procedure and the threshold parameters may comprise one or more pre-agreed risk parameters. If the pre-agreed threshold parameters are satisfied, the (at least one) verification provider may immediately perfect (e.g., “bless”) the transaction request and broadcast the now-perfected blockchain transaction to the blockchain network. Perfecting the transaction request may include generating a second signature using a second private key (e.g., created and maintained by the verification provider) and optionally imposing a pre-agreed surcharge.

In the absence of pre-agreed threshold parameters, or if the pre-agreed threshold parameters are not satisfied during the assessment, the operation may further include generating, by at least one of the one or more verification providers, one or more verification offers including a respective one or more second signatures and, optionally, in some examples, one or more risk-related surcharges. Each of the one or more second signatures may be generated by a respective one of the one or more verification providers using a second private key (e.g., created and maintained by the verification provider). In some embodiments, the one or more verification providers may transmit one or more denials, rather than verification offers.

In an example operation of the present disclosure, the first verification provider to assess the risk and perfect the transaction may prevail and capture a previously-agreed fee. In the event that the risk analysis performed by the verification provider determines that a risk surcharge is needed to offset risk, the operation may include transmitting the one or more verification offers to the payer client device and prompting the payer computing device to confirm the blockchain transaction by selecting at least one of the one or more verification offers and receiving, from the payer client device, a selection of at least one offer of the one or more verification offers (thereby providing a perfected blockchain transaction). The operation may conclude with broadcasting the perfected blockchain transaction to the blockchain network.

In some examples, systems and methods of the present disclosure may leverage the breakthroughs in real-time risk assessment that have been created via high-frequency trading to allow verification providers to compete for individual transaction fees, while isolating the payer from reliance on any single provider.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating a computing environment for authorizing blockchain transactions, according to an exemplary embodiment.

FIG. 1B is a block diagram visually depicting one or more parties to a blockchain transaction, according to an exemplary embodiment.

FIG. 2 is a block diagram illustrating a computing environment for authorizing blockchain transactions including a verification network, according to an exemplary embodiment.

FIG. 3 is a flow diagram illustrating a method of authorizing a blockchain transaction using a verification network, according to one or more exemplary embodiments.

FIG. 4 is a flow diagram illustrating communication among one or more computing components for authorizing a blockchain transaction using a verification network, according to one or more exemplary embodiments.

FIG. 5A is a block diagram illustrating one or more screenshots of a client computing device, according to one or more exemplary embodiments.

FIG. 5B is a block diagram illustrating one or more screenshots of a client computing device, according to one or more exemplary embodiments.

FIG. 6 is a block diagram illustrating a computing environment, according to one or more exemplary embodiments.

DETAILED DESCRIPTION

Aspects of the present disclosure relate to systems, methods and non-transitory computer readable media for authorizing a blockchain transaction. In some examples, system may include a verification network in communication with at least a payer computing device associated with a payer, a verification pool that includes one or more independent third-party verification computing systems (e.g., verification providers or verification institutions), and a blockchain network. In some examples, the verification network includes a computing system having a processor and a memory having programming instructions stored thereon, where the programming instructions, when executed by the processor, cause the system to perform an operation for authorizing the blockchain transaction. The operation includes receiving, from the payer computing device, a partially-signed blockchain transaction (e.g., a transaction request). The transaction may include a first signature, where the first signature may be generated by a first private key created and managed by the payer (e.g., a first private key associated with the payer). In one example, the first signature may be the only signature included in the (partially-signed) transaction. In some examples, the partially-signed transaction may be enriched by the verification network with situational details such as (without being limited to) time, value, geolocation, merchant statistics and/or any suitable information that may be useful to a verification provider in analyzing the likelihood of attempted fraud. Since, in an exemplary embodiment of the present disclosure, the payer private key must be protected by the payer, the nature of the present disclosure significantly mitigates the impact of unauthorized access to this payer private key, thereby significantly increasing the attractiveness of existing backup solutions.

The operation of the verification network further includes broadcasting the partially-signed transaction and details relating to one or more pre-agreed threshold parameters (e.g., risk assessment details) to the one or more verification providers. The operation may further include assessing, by at least one verification provider from among the verification pool, the one or more pre-agreed threshold parameters associated with the partially-signed transaction. The assessing may be a part of a broader risk analysis procedure and the threshold parameters may comprise one or more pre-agreed risk parameters. If the pre-agreed threshold parameters are satisfied, the (at least one) verification provider may immediately perfect (e.g., “bless”) the transaction request and broadcast the now-perfected blockchain transaction to the blockchain network. Perfecting the transaction request may include generating a second signature using a second private key (e.g., created and maintained by the verification provider) and optionally imposing a pre-agreed surcharge.

In the absence of pre-agreed threshold parameters, or if the pre-agreed threshold parameters are not satisfied during the assessment, the operation may further include generating, by at least one of the one or more verification providers, one or more verification offers including a respective one or more second signatures and, optionally, in some examples, one or more risk-related surcharges. Each of the one or more second signatures may be generated by a respective one of the one or more verification providers using a second private key (e.g., created and maintained by the verification provider). In some embodiments, the one or more verification providers may transmit one or more denials, rather than verification offers.

In an example operation of the present disclosure, the first verification provider to assess the risk and perfect the transaction may prevail and capture a previously-agreed fee. In the event that the risk analysis performed by the verification provider determines that a risk surcharge is needed to offset risk, the operation may include transmitting the one or more verification offers to the payer client device and prompting the payer computing device to confirm the blockchain transaction by selecting at least one of the one or more verification offers and receiving, from the payer client device, a selection of at least one offer of the one or more verification offers (thereby providing a perfected blockchain transaction). The operation may conclude with broadcasting the perfected blockchain transaction to the blockchain network.

In some examples, systems and methods of the present disclosure may leverage the breakthroughs in real-time risk assessment that have been created via high-frequency trading to allow verification providers to compete for individual transaction fees, while isolating the payer from reliance on any single provider.

In conventional blockchain transaction systems, two parties may directly transact with one another. For example, a payee may share a public address (e.g., public key) to which a payer is to transmit an amount of cryptocurrency. The payer may then initiate a transaction that has one or more inputs and one or more outputs. The one or more inputs may correspond to a public key of the payer (e.g., an address from which the cryptocurrency originates) and a signature that was generated using a private key of the payer. The one or more outputs may correspond to the public address of the payee. The transaction may be transmitted to a blockchain network for verification (e.g., to verify that the payer actually has the amount of digital assets, e.g., cryptocurrency, that the payer alleges to have, and that the payer has not transmitted these digital assets).

Such conventional systems, however, suffer from one or more limitations. For example, should a user's private key become compromised (e.g., stolen), the fraudulent party that obtained the user's private key has necessarily stolen all cryptocurrency associated therewith. Further, should a user lose their private key, all cryptocurrency associated therewith is effectively lost.

One or more systems currently exist to combat the limitations of a single signature transaction. For example, one or more systems may provide a multi-signature service. A multi-signature transaction requires that two or more signatures be generated for each transaction. With conventional multi-signature systems, each system functions to provide the additional signature that may be necessary to perfect a transaction. In other words, in a conventional multi-signature service, a signature from the payer and a signature from the multi-signature service is needed for any given transaction.

The one or more techniques disclosed herein provide a verification network that improves upon conventional multi-signature services. For example, the verification network described herein acts as a middleman between parties to a transaction and one or more trusted verification institutions. Upon receiving a transaction request from a payer, the verification network may broadcast a verification request to a pool of pre-defined verification institutions. Each verification institution may be a trusted entity that can “bless” or verify the transaction. At least one signature is needed from the pool of verification institutions to perfect (i.e., “bless”) the respective transaction. Accordingly, the system of the present disclosure eliminates dependency on a single entity, as currently required by conventional multi-signature services, and instead relies on a pool, or network, of verification institutions that may verify the transaction. Moreover, the system of the present disclosure also eliminates control over a payer's digital assets that may result from two or more parties colluding to release or take control of the digital assets.

The term “user” as used herein includes, for example, a person or entity that owns a computing device (which may include a wireless device); a person or entity that operates or utilizes a computing device; or a person or entity that is otherwise associated with a computing device (which may include a wireless device). It is contemplated that the term “user” is not intended to be limiting and may include various examples beyond those described.

Moreover, examples of the present disclosure described below refer to blockchain-based transactions involving digital assets such as, for example (but not limited to), cryptocurrency. In general, systems and methods of the present disclosure may be configured to authorize transactions involving any suitable digital asset that may be tokenized, including security tokens, tokenized real estate, and one or more cryptocurrencies (e.g., digital or virtual currency that may use cryptography for security). In general, cryptocurrency may include, without being limited to, Bitcoin, Litecoin, Ether, etc. In fact, for purposes of this disclosure, the term cryptocurrency should be understood to include any digital or virtual assert or currency.

In some examples, transactions with respect to the present disclosure are referred to as blockchain transactions. In other examples, transactions are referred to as cryptocurrency transactions. As used herein, both blockchain transactions and cryptocurrency transactions refer to transactions of cryptocurrency (or any suitable digital asset) that uses a blockchain network.

FIG. 1A is a block diagram illustrating a computing environment 100 for authorizing blockchain transactions, according to an example embodiment. Computing environment 100 may include at least client device 102, client device 104, verification pool 106, verification network 105 and blockchain network 108. Communication among client device 102, client device 104, verification pool 106 and blockchain network 108 may be performed via verification network 105. Although one client device 102 and one client device 104 are shown in FIG. 1A, it is understood that environment 100 may include any number of client devices 102 and/or any number of client devices 104.

In the examples described herein, client device 102 may be operated by a user representing a payer. For example, client device 102 may be a mobile device, a tablet, a desktop computer, or any computing system having the capabilities described herein.

In the examples described herein, client device 104 may be operated by a user representing a payee. For example, client device 104 may be a mobile device, a tablet, a desktop computer, or any computing system having the capabilities described herein.

Client device 102 and client device 104 may communicate with verification network 105. Verification network 105 may be representative of a service that supports multi-signature functionality. In general, multi-signature functionality is a service that requires two or more signatures (e.g., two or more private keys) to authorize a cryptocurrency transaction. Verification network 105 may be configured to store one or more private keys associated with each user or subscriber. For example, verification network 105 may be configured to store one or more private keys associated with at least the payer to a transaction (e.g., client device 102).

Unlike conventional multi-signature services, verification network 105 does not perform the verification of cryptocurrency transactions between parties to a transaction. Rather, verification network 105 may be configured to facilitate the verification thereof by broadcasting a proposed transaction to verification pool 106.

Verification pool 106 may be representative of one or more trusted financial institutions (e.g., verification providers) that may verify a cryptocurrency transaction. In other words, verification pool 106 may include one or more financial institutions that are required to act as a second party to a multi-signature transaction. Verification pool 106 may include one or more verification institutions 1101, 1102, . . . , 110. (generally “verification institution 110”, where n is an integer greater than or equal to 1). In some embodiments, each verification institution 110 may be pre-approved with verification network 105. When a transaction request is received from client device 102 at verification network 105, verification network 105 may broadcast a verification request to each verification institution 110. Each verification institution 110 may then assess a risk associated with verifying the transaction. Based on this assessment, each verification institution 110 may generate a verification offer (described further below) to be transmitted to client device 102. In some embodiments, one or more verification institutions 110 may prompt client device 102 to authenticate with verification institution 110. For example, a verification institution 110 may request verification network 105 to transmit an identification request to the payer (e.g., client device 102) to confirm the identity of the payer for risk analysis purposes. Because each verification institution 110 is competing with one or more other verification institutions 110, each verification institution 110 may race to assess the risk associated with a transaction and generate an offer that competes with other offers. Accordingly, those skilled in the art may readily understand that verification institutions 110 may balance the trade-off between quickly generating a verification offer and accurately assessing a risk associated with the verification offer.

When each verification institution 110 generates a verification offer, verification institution 110 may access a private key associated with the payer (e.g., created and/or managed by the payer) via verification network 105. Each verification institution 110 may then generate a second signature for the transaction, using the private key hosted by verification network 105. The second signature for the transaction may be transmitted by verification institution 110 to verification network 105 with the verification offer. In some examples, the second signature may represent a private key created and/or maintained by verification institution 110 (a verification provider) and/or provided via verification network 105. Accordingly, verification network 105 receives at least two signatures (e.g., a first signature from client device 102 and a second signature from each verification institution 110) which are required for the transaction.

In some embodiments, each verification institution 110 may have a pre-established relationship with a user (or subscriber) of verification network 105. For example, each verification institution 110 may prompt the user to submit a verification application, such that each verification institution 110 may vet the user similar to a credit card application process. Accordingly, for each user, each verification institution 110 may set one or more pre-arranged limits, parameters, or contractual duties for each transaction. For example, for a given user, verification institution 110 may set a transaction limit of Bitcoin, Litecoin, Ether, etc. to a transaction. In another example, a verification institution 110 may attempt to limit its liability to a transaction, by contractually agreeing with each user that verification institution 110 is only liable for up to 50% of the transaction amount. Accordingly, when selecting a verification offer, a user may base the decision on, for example, which verification institution 110 offers the best refund policy.

Verification network 105 may receive the one or more verification offers from the one or more verification institutions 110 (i.e., verification instate 110 ₁, 110 ₂, . . . , 110 _(n)). Verification network 105 may transmit the one or more verification offers to client device 102 and prompt client device 102 to select an offer among the verification offer(s). Verification network 105 may receive from client device 102 an indication of a selection of a particular verification offer. Verification network 105 may then broadcast the transaction to blockchain network 108 (responsive to the selected offer) for posting. Blockchain network 108 may include one or more computing devices for processing a blockchain transaction, by generating a block that is added to a blockchain that includes a record for the transaction. The blockchain represents a decentralized, public ledger of all transactions of a blockchain-based currency.

The role played by verification institution 110 is similar to a verifier of a transaction. For example, verification institution 110 may be responsible for verifying that the payer (e.g., client device 102) is indeed the payer and that the payer has the alleged amount of cryptocurrency for the transaction.

In conventional blockchain systems, transactions between a payer and payee are irreversible, because once a payer relinquishes control of the amount of cryptocurrency, the payer can only be made whole if the payee agrees to refund the payer. The present system addresses this limitation by providing an intermediary verification network 105 and verification pool 106. When one or more verification institutions 110 assess a risk associated with a particular transaction, proposes a verification offer, and receives an acceptance of that verification offer, the respective verification institution 110 has taken responsibility for the transaction. In other words, if a fraudulent third party gained access to the payer's account, verification institution 110 is responsible for making the payer whole (i.e., refunding the payer the amount transferred to the payee). In this manner, verification institution 110 (e.g., a verification provider) may “eat the charges” for any risk miscalculations, thereby reducing the impact of fraud on the payer. Moreover, because various verification institutions 110 (e.g., verification providers) of verification pool 106 may compete to perfect a transaction through one or more verification offers, environment 100 may spread out any risk miscalculations among the verification providers of verification pool 106, thereby reducing any concentration risk that is conventionally posed by relying on a single verification service provider.

Further, because verification network 105 supports multi-signature functionality, for each transaction, two or more signatures are necessary to perfect the transaction. In conventional multi-signature systems (e.g., two-signature system), any individual party that has access to at least two of the payer's private keys may take control of the payer's cryptocurrency. Similarly, in conventional systems, any two actors may collude to release or take control of an individual's cryptocurrency by gaining access to at least two private keys of the individual. The present disclosure addresses these limitations of conventional systems by anticipating the possibility that, when the proposed transaction is broadcast to verification pool 106, two or more verification institutions 110 may collude to release the payer's funds. To address this, the computing device associated with the payer (e.g., client device 102) is a mandatory party to the transaction. In other words, even though one or more verification institutions 110 in verification pool 106 may collude and provide the necessary number of signatures required for a specific multi-signature transaction, verification network 105 will not perfect the transaction without receiving a signature from the payer.

Examples of client device 102, verification network 105 and verification institution 110 _(n) are described further below with respect to FIG. 2 .

FIG. 1B is a block diagram 150 visually depicting one or more parties to a cryptocurrency transaction, according to example embodiments. As shown, block diagram 150 includes verification institution 110 ₁, verification institution 110 ₂, and verification institution 110 _(n) as the one or more verification institutions 110. For this transaction, at least two signatures are needed to perfect the transaction from payer to payee.

As illustrated, the verification offers 122-1 and 122-2 submitted by institution 110 ₁ and institution 110 ₂, respectively, have been selected by payer (e.g., client device 102). In conventional systems, because a minimum of two signature are required, the signature (2/2) generated by verification institution 110 ₁ and the signature (2/2) generated by verification institution 110 ₂ would be sufficient to perfect the transaction. Those skilled in the art may readily understand that, if verification network 105 were compromised, and two or more private keys associated with client device 102 were accessed, verification institution 110 ₁ and verification institution 110 ₂ could collude to release or gain access to the payer's cryptocurrency. However, such signatures would not be sufficient to perfect the transaction in computing environment 100 because client device 102 (including signature 120 generated by client device 102) is a mandatory party to the transaction. Accordingly, at least one of the at least two required signatures must be generated by client device 102 (or more generally, the payer). Thus, in the example shown in FIG. 1B, signatures 124 to perfect the transaction (e.g., for payment) includes signatures (2/3) (i.e., signature 120 of client device 102 and signatures (2/2) of respective verification institutions 110 ₁.110 ₂).

FIG. 2 is a block diagram illustrating computing environment 200 for authorizing blockchain transactions, according to one or more exemplary embodiments. As illustrated, computing environment 200 includes at least client device 102, at least one verification institution 110, and verification network 105. Client device 102, verification institution 110 and verification network 105 may communicate via at least one network 205.

Network 205 may be of any suitable type, including individual connections via the Internet, such as cellular or Wi-Fi networks. In some embodiments, network 205 may connect terminals, services, and mobile devices using direct connections, such as, without being limited to, radio frequency identification (RFID), near-field communication (NFC), Bluetooth™, low-energy Bluetooth™ (BLE), Wi-Fi™, ZigBee™, ambient backscatter communication (ABC) protocols, universal serial bus (USB), wide area network (WAN), or local area network (LAN). Because the information transmitted may be personal or confidential, security concerns may dictate one or more of these types of connections be encrypted or otherwise secured. In some embodiments, however, the information being transmitted may be less personal, and therefore, the network connections may be selected for convenience over security.

Network 205 may include any type of computer networking arrangement used to exchange data. For example, network 205 may be the Internet, a private data network, a virtual private network using a public network and/or other suitable connection(s) that enables components in computing environment 200 to send and receive information therebetween.

Client device 102 may include application 252 and wallet 254. Application 252 may be representative of a web browser that allows access to a website or a stand-alone application. Client device 102 may access application 252 to access functionality of verification network 105. Client device 102 may communicate over network 205 to request a webpage, for example, from web client application server 206 of verification network 105. For example, client device 102 may be configured to execute application 252 to access one or more functionalities of verification network 105. The content that is displayed to client device 102 may be transmitted from web client application server 206 to client device 102, and subsequently processed by application 252 for display through an interactive graphical user interface (GUI) rendered by client device 102.

Wallet 254 may be representative of a digital storage location on client device 102. Wallet 254 may be configured to store one or more key pairs 255 associated with a user's blockchain account (e.g., account 212). As illustrated, each key pair 255 may include a private key 256 and a corresponding public key 258.

Each private key 256 may be an alphanumeric string that allows a user of client device 102 to transmit (e.g., spend) one or more cryptocurrencies to another individual or entity (i.e., another cryptocurrency address). Private key 256 may be used to sign each cryptocurrency transaction. For example, a user may input private key 256 into a signature algorithm which outputs a signature that may be verified by verification network 105. Any individual or entity that has access to private key 256 may be able to access the one or more cryptocurrencies corresponding to private key 256.

Each public key 258 may correspond to a respective private key 256. In some embodiments, public key 258 may be derived from its respective private key 256. Public key 258 may be an alphanumeric string that corresponds to a public address of an individual or entity. For example, when a payer or transmitter attempts to transmit an amount of cryptocurrency to a user of client device 102, the payer or transmitter directs the transmittal to the address defined by public key 258. Public key 258 may be public because, although derived from a respective private key 256, it is near impossible to reverse engineer private key 256.

Verification network 105 may include management system 202 and database 204. Management system 202 may be representative of a computing system. Management system 202 may include web client application server 206, account handler 208, transaction agent 209, and verification agent 210.

Each of account handler 208, transaction agent 209, and verification agent 210 may be comprised of one or more software modules. The one or more software modules may be collections of code or instructions stored on a media (e.g., memory of management system 202) that represent a series of machine instructions (e.g., program code) that implements one or more algorithmic steps. Such machine instructions may be the actual computer code that a processor of management system 202 interprets to implement the instructions or, alternatively, may be a higher level of coding of the instructions that is interpreted to obtain the actual computer code. The one or more software modules may also include one or more hardware components. One or more aspects of the algorithm may be performed by the hardware components (e.g., circuitry) itself, rather than as a result of an instruction.

Account handler 208 may be configured to manage one or more accounts 212 associated with one or more users. For example, account handler 208 may communicate with database 204. As illustrated, database 204 may include one or more accounts 212. Each account 212 may include one or more key pairs 215 and one or more transactions 218. Each key pair 215 may include a private key 214 and a corresponding public key 216. Account handler 208 may generate one or more key pairs 215 upon a user registering with verification network 105. In some embodiments, account handler 208 may generate one or more key pairs 255 stored on client device 102.

Each private key 214 may be an alphanumeric string that allows one or more verification institutions 110 to verify a particular transaction request. Private key 214 may be used to sign each cryptocurrency transaction. For example, a verification institution 110 may access a private key 214 from verification network 105, and input private key 214 into a signature algorithm which outputs a signature that may be verified by verification network 105. Any individual or entity that has access to private key 214 may be able to access the one or more cryptocurrencies corresponding the private key 214.

Each public key 216 may correspond to a respective private key 214. In some embodiments, public key 216 may be derived from its respective private key 214. Public key 216 may be an alphanumeric string that corresponds to a public address associated with an individual or entity. For example, when a verification institution 110 assesses a risk associated with a transaction request, verification institution 110 may identify a payer using public key 216. Public key 216 may be public because, although derived from a respective private key 214, it is near impossible to reverse engineer private key 214.

Transaction agent 209 may be configured to manage one or more transactions 218 associated with each account 212. For example, transaction agent 209 may act as a “middle-man” between client device 102 and one or more verification institutions 110. In operation, for example, transaction agent 209 may transmit a transaction request to one or more verification institutions 110. Each of the one or more verification institutions 110 may race to assess the risk associated with verifying the transaction, and provide an offer to the payer for verifying the transaction. For example, each of the one or more verification institutions 110 may transmit to verification network 105 a willingness to verify the transaction along with a fee for their verification (e.g., a verification offer). The verification offer may, in turn, be transmitted from verification network 105 to client device 102 for display. Upon receiving input from client device 102 that corresponds to a selection of a verification offer, verification network 105 may transmit the offer acceptance to the respective verification institution 110.

After a transaction is finalized between a payer (e.g., client device 102) and a payee (e.g., client device 104), transaction agent 209 may record the transaction in database 204. For example, transaction agent 209 may record the payer to the transaction and the payee to the transaction, along with the transaction amount, in one or more transactions 218. Accordingly, if, for example, the transaction was later deemed fraudulent, transaction agent 209 may notify the verification institution 110 that verified the transaction, such that verification institution 110 can reimburse the payer to the transaction.

Verification agent 210 may be configured to verify one or more transactions between a payer (e.g., client device 102) and a payee (e.g., client device 104). Verification agent 210 may, for example, verify a first signature transmitted from client device 102 to verification network 105 that signals the initiation of the transaction. The first signature may correspond to a first signature needed for a multi-signature transaction. Verification agent 210 may further be configured to verify a second signature transmitted from a verification institution 110, in response to generation of a verification offer from verification institution 110. The second signature may correspond to a second signature (or additional signature) needed for a multi-signature transaction.

Upon receiving the necessary number of signatures required for the multi-signature transaction (e.g., two or more signatures), verification institution 110 may communicate with transaction agent 209 to complete the transaction. Transaction agent 209 may broadcast the completed transaction to blockchain network 108, such that the transaction may be posted thereto.

Verification institution 110 may be representative of a computing system associated with any suitable entity such as, for example, a particular financial institution or other trusted entity. Verification institution 110 may include computing device 260. Computing device 260 may be a mobile device, a tablet, a desktop computer, or any computing system having the capabilities described herein. Computing device 260 may include application 262 and risk analyzer 264.

Application 262 may be representative of a web browser that allows access to a website or a stand-alone application. Computing device 260 may access application 262 to access functionality of verification network 105. Computing device 260 may communicate over network 205 to request a webpage, for example, from web client application server 206 of verification network 105. For example, computing system 260 may be configured to execute application 262 to access one or more functionalities of verification network 105. The content that is displayed to computing device 260 may be transmitted from web client application server 206 to computing device 260, and subsequently processed by application 262 and, in some examples, may be displayed through a GUI rendered by computing system 260.

Risk analyzer 264 may be comprised of one or more software modules. The one or more software modules may be collections of code or instructions stored on a media (e.g., memory of computing device 260) that represent a series of machine instructions (e.g., program code) that implements one or more algorithmic steps. Such machine instructions may be the actual computer code a processor of computing device 260 interprets to implement the instructions or, alternatively, may be a higher level of coding of the instructions that is interpreted to obtain the actual computer code. The one or more software modules may also include one or more hardware components. One or more aspects of the algorithm may be performed by the hardware components (e.g., circuitry) itself, rather than as a result of an instruction.

Risk analyzer 264 may be configured to assess a risk associated with verifying a cryptocurrency transaction between the payer (e.g., client device 102) and the payee (e.g., client device 104). In some embodiments, risk analyzer 264 may assess the risk associated with verifying the cryptocurrency transaction by taking in account one or more parameters that include, but are not limited to, a current location of client device 102 (e.g., at a location associated with the user), an amount of cryptocurrency to be transmitted, a frequency of transactions between the payer (e.g., client device 102) and the payee (e.g., client device 104), the identity of the payee (e.g., a merchant), the time of day of the transaction, a purchase history of the payer, and the like. In some examples, risk analysis by risk analyzer 264 may include contacting the payer (e.g., via a call or text) to confirm the transaction. Based on the risk assessment performed by risk analyzer 264, verification institution 110 may generate a verification offer to be transmitted to client device 102.

Because, however, verifying the transaction may subject verification institution 110 to financial risk (e.g., if the transfer from client device 102 to client device 104 was fraudulent), verification institution 110 may charge the payer a fee for their verification service. For example, when risk analyzer 264 determines that there is minimal risk associated with verifying the transaction, verification institution 110 may propose a minimal fee to client device 102 in the verification offer. In another example, when risk analyzer 264 determines that there is a higher risk associated with verifying the transaction, verification institution 110 may propose a higher fee to client device 102 in the verification offer. Further, in some embodiments, verification institution 110 may propose a surge fee to a transaction. For example, in those embodiments in which verification network 105 broadcasts a higher volume of verification requests, verification institution 110 may propose a surge fee for its services.

FIG. 3 is a flow diagram illustrating a method 300 of authorizing a blockchain transaction using verification network 105, according to one or more exemplary embodiments. Method 300 may begin at step 302.

At step 302, verification network 105 may receive a transaction request from client device 102 (e.g., via a payment card, an application, a mobile phone, online, etc.). The transaction request may include at least a designation of the payer (e.g., client device 102), the payee (e.g., client device 104), and the amount of cryptocurrency specified in the transaction. For example, the transaction request may include a public address (e.g., public key 258) corresponding to client device 102, a signature generated by client device 102 using private key 256), a public address corresponding to client device 104, and the amount specified in the transaction. Further, in some embodiments, the transaction request may also specify a number of signatures required for the multi-signature authorization. For example, in some embodiments, the transaction request may specify that at least one verification institution 110 is necessary for verification. In another example, the transaction request may specify that at least two of the verification institutions 110 are necessary for verification. In some examples, the transaction request may represent a partially-signed blockchain transaction, that may include a first signature generated by the client device 102 using private key 256, but may not include any second signatures needed to perfect the blockchain transaction.

At step 304, verification network 105 may broadcast a verification request to verification pool 106. The verification request may include one or more parameters associated with the transaction request. Such parameters may include, but are not limited to, the public address (e.g., public key 258) corresponding to client device 102, a public address associated with client device 104, and the amount specified in the transaction. In some examples, verification network 105 may determine and include situational details associated with the partially-signed transaction that may be useful (to verification pool 106) in analyzing a likelihood of attempted fraud. Non-limiting examples of situational details may include a time of the transaction, a value of the transaction, a geolocation of client device 102, any merchant statistics, etc. In some examples, the verification request broadcast by verification network 105 may include the partially-signed transaction (from client device 102) and any additional information and/or risk assessment details (e.g., parameters, situational details, etc.) provided by verification network 105. Thus, in some examples, the partially-signed transaction may be enriched by the information provided by verification network 105. In some embodiments, the one or more parameters may further include a number of additional signatures needed from verification pool 106 to complete the multi-signature transaction.

At step 306, verification network 105 may receive one or more verification offers based on a risk analysis of the transaction request. For example, verification network 105 may receive one or more verification offers from one or more verification institutions 110 to be transmitted to client device 102. Each verification offer may be generated by a verification institution 110 based on a determined risk with verifying the transaction. Each verification offer may include a verification charge associated therewith.

At step 308, verification network 105 may prompt the payer to select a verification offer from a respective verification institution 110. Verification network 105 may transmit the one or more verification offers to client device 102 for display. Client device 102 may, in turn, push the one or more verification offers to client device 102, prompting the payer to select from among the one or more verification offers.

At step 310, verification network 105 may receive, from client device 102, an indication of a selection of at least one verification offer. For example, client device 102 may receive input via a GUI displayed thereon, which corresponds to a selection of a verification offer from a particular verification institution 110. Client device 102 may translate the input to a message that is transmitted to verification network 105. The message may indicate the verification offer selected by the payer.

At step 312, verification network 105 may broadcast the transaction between client device 102 and client device 104 to blockchain network 108. For example, upon determining that the necessary number of signatures required by the transaction request is met, verification network 105 may transmit the transaction between payer and payee to blockchain network 108 for posting to the blockchain. In some examples, the transaction may also take into account any surcharge fee associated with the selected verification offer(s).

In some examples, the verification request (step 304) may include the partially-signed transaction (e.g., the transaction request) and details relating to one or more pre-agreed threshold parameters (e.g., risk assessment details). Responsive to the broadcasted verification request (step 304), at least one verification institution 110 (e.g., verification institution 110 ₂) among verification pool 106 may assess the pre-agreed threshold parameter(s) associated with the partially-signed transaction. The assessing may be a part of a broader risk analysis procedure and the threshold parameter(s) may comprise one or more pre-agreed risk parameters. If the pre-agreed threshold parameter(s) are satisfied, the (at least one) verification institution 110 (e.g., verification institution 110 ₂) may immediately perfect (e.g., “bless”) the transaction request and broadcast the now-perfected blockchain transaction to blockchain network 108 (e.g., bypassing steps 306-310). Perfecting the transaction request may include generating a second signature using a second private key (e.g., created and maintained by the verification provider) and optionally imposing a pre-agreed surcharge. In some examples, verification institution 110 (e.g., verification institution 1102) may broadcast the perfected transaction directly to blockchain network 108 and/or via verification network 105. In some examples, a first verification institution 110 (e.g., verification institution 1102) to assess the risk, perfect the transaction (according to the previously-agreed upon fee) and broadcast the perfected transaction (e.g., the now fully-signed transaction including the first signature from client device 102 and the second signature from verification institution 1102) may prevail and capture the previously-agreed fee.

In the absence of pre-agreed threshold parameter(s), or if the pre-agreed threshold parameter(s) are not satisfied during the assessment, the operation may further include generating, by at least one of verification institutions 110, a respective one or more verification offer(s) including a respective one or more second signatures and, optionally, in some examples, one or more risk-related surcharges. Each of the second signature(s) may be generated by a respective one of verification institutions 110 using a respective second private key (e.g., created and maintained by a respective verification institution 110). The verification offer(s) may be transmitted to and received by verification network 105 (step 306) and step 306 may proceed to steps 308-310 (as discussed above). In some embodiments, verification institution(s) 110 may transmit one or more denials, rather than verification offers. Thus, in some examples,when verification institution(s) 110 determine, from the risk analysis, that a risk surcharge is needed to offset risk, the verification offer(s) may include the requested surcharge and an indication to prompt client device 102 to select a verification offer. Based on the indication to prompt the payer, verification network 105 may prompt client device 102 to select a verification offer and may receive a selection from client device 102 (as described above at steps 308-310). Responsive to the selection from client device 102, verification network 105 may then broadcast the now perfected transaction (e.g., including the first signature from client device 102 and the second signature in the selected verification offer) to blockchain network 108 (step 312). In this manner, verification network 105 may cause the payer (via client device 102) to confirm the blockchain transaction.

FIG. 4 is a flow diagram illustrating a method 400 of communication among one or more computing components for authorizing a blockchain transaction using verification network 105, according to one or more exemplary embodiments. Method 400 may begin at step 402.

At step 402, client device 102 may transmit a transaction request to verification network 105. The transaction request may include at least a designation of the payer (e.g., client device 102), the payee (e.g., client device 104), and the amount of cryptocurrency specified in the transaction. For example, the transaction request may include a public address (e.g., public key 258) corresponding to client device 102, a signature generated by client device 102 using private key 256), a public address corresponding to client device 104, and the amount specified in the transaction. Further, in some embodiments, the transaction request may also specify a number of signatures required for the multi-signature authorization. For example, in some embodiments, the transaction request may specify that at least one verification institution 110 is necessary for verification. In another example, the transaction request may specify that at least two of the verification institutions 110 is necessary for verification.

At step 404, verification network 105 may receive the transaction request from client device 102. In some embodiments, upon receiving the transaction request from client device 102, verification network 105 may verify that the payer has indeed signed the transaction. For example, verification network 105 may verify that client device 102 transmitted the signature for the transaction.

At step 406, verification network 105 may broadcast a verification request to verification pool 106. The verification request may include one or more parameters associated with the transaction request. Such parameters may include, but are not limited to, the public address (e.g., public key 258) corresponding to client device 102, a public address associated with client device 104, and the amount specified in the transaction. In some embodiments, the one or more parameters may further include a number of additional signatures needed from verification pool 106 to complete the multi-signature transaction.

At step 408, verification institution 110 may receive the broadcasted verification request from verification network 105. Although the below operations are discussed generally with respect to one or more verification institutions 110, those skilled in the art may readily understand that it is not required for all verification institutions 110 in verification pool 106 to perform all of the operations described below.

At step 410, verification institution 110 may assess a risk associated with verifying the transaction request. For example, risk analyzer 264 may be configured to assess a risk associated with verifying the cryptocurrency transaction between the payer (e.g., client device 102) and the payee (e.g., client device 104). In some embodiments, risk analyzer 264 may asses the risk associated with verifying the cryptocurrency transaction by taking in account one or more parameters that include, but are not limited to, a current location of client device 102 (e.g., at a location associated with the user), an amount of cryptocurrency to be transmitted, a frequency of transactions between the payer (e.g., client device 102) and the payee (e.g., client device 104), and the like. Based on the risk assessment performed by risk analyzer 264, verification institution 110 may generate a verification offer to be transmitted to client device 102.

At step 412, verification institution 110 may assign a verification fee to the verification offer based on the risk assessment analysis. For example, verification institution 110 may assign a fee to their verification service based on the risk associated with verifying a particular transaction. For example, if risk analyzer 264 determines that there is minimal risk associated with verifying the transaction, verification institution 110 may propose a minimal fee to client device 102 in the verification offer. In another example, if risk analyzer 264 determines that there is a higher risk associated with verifying the transaction, verification institution 110 may propose a higher fee to client device 102 in the verification offer.

At step 414, verification institution 110 may access a private key associated with the payer. For example, upon generating a verification offer, verification institution 110 may request from verification network 105 a private key (e.g., private key 214) that is hosted by verification network 105 and associated with the payer (e.g., client device 102).

At step 416, verification institution 110 may generate a signature using the accessed private key. For example, verification institution 110 may generate a second (or third, fourth, etc.) signature for the transaction using private key 214. By generating a second signature prior to transmitting the verification offer to client device 102, the transaction may be completed as soon as the payer selects a verification offer.

At step 418, verification institution 110 may transmit the verification offer and the second (or additional) signature to verification network 105. At step 420, verification network 105 may receive the verification offer and the second signature from verification institution 110.

At step 422, verification network 105 may prompt the payer to select a verification offer from a respective verification institution 110. Verification network 105 may transmit the one or more verification offers to client device 102 for display. The verification offer may include the verification fee associated therewith.

At step 424, client device 102 may receive the prompt from verification network 105. For example, client device 102 may receive the one or more verification offers from verification network 105 via application 252 executing thereon.

At step 426, client device 102 may generate a GUI displaying the one or more verification offers. The GUI generated by client device 102 may be displayed to the payer via a display associated with client device 102. For example, the GUI may be displayed via an external display device (e.g., a monitor) associated with client device 102. In another embodiment, the GUI may be displayed via a touchscreen associated with client device 102. The GUI may include the one or more verification offers and the one or more verification fees associated therewith.

At step 428, client device 102 may receive an input that corresponds to a selection among the verification offer(s). For example, client device 102 may receive an input, via the GUI, a selection of a verification offer. At step 430, client device 102 may transmit a verification offer acceptance to verification network 105.

At step 430, verification network 105 may receive the selection of the verification offer acceptance from client device 102. At step 432, verification network 105 may notify a respective verification institution 110 of the verification offer acceptance. For example, verification network 105 may transmit a message to a respective verification institution 110 associated with the verification offer.

At step 434, verification network 105 may record the transaction details in database 204. for example, verification network 105 may record the transaction date, the transaction amount, the payer public address, the payee public address, any verification fees and one or more verification institutions 110 associated with one or more accepted verification offers in database 204. By recording the transaction details in database 204, should the transaction later be deemed fraudulent (e.g., a fraudulent third party obtained the payer's private key (e.g., private key 256), the transaction may be reversible. For example, the one or more verification institutions 110 whose verification offers were accepted are now liable for refunding the payer the transaction amount.

At step 436, verification network 105 may broadcast/post the transaction between client device 102 and client device 104 to blockchain network 108. For example, upon determining that the necessary number of signatures required by the transaction request is met, verification network 105 may transmit the transaction between payer and payee to blockchain network 108 for posting to the blockchain. In some examples, the transaction may also reflect any verification fees.

Although not shown in FIG. 4 , as discussed above, in some examples, after step 408 (e.g., at step 410), verification institution(s) 110 may assess pre-agreed threshold parameter(s) associated with the transaction request and determine whether the pre-agreed threshold parameter(s) have been satisfied. If at least one of verification institutions 110 determine that the pre-agreed threshold parameter(s) are satisfied, the at least one verification institution 110 may perfect the blockchain transaction (as discussed above) and broadcast the perfected blockchain transaction to blockchain network 108 (thereby bypassing, for example, steps 412-434). If the pre-agreed threshold parameter(s) are not satisfied, the process may proceed according to steps 412-436.

FIG. 5A is a block diagram 500 illustrating one or more screenshots of client computing device 502, according to one or more exemplary embodiments. As illustrated, client device 502 may be a mobile device associated with a payer. For example, client device 502 may be associated with client device 102 (explained in detail above). Client device 502 may include display 504. Display 504 may be currently displaying screenshot 505. Screenshot 505 may illustrate an example GUI that may be generated and displayed to the payer upon receiving one or more verification offers from verification network 105.

As shown, screenshot 505 includes one or more verification offers 503 ₁, 503 ₂, and 503 ₃ (generally “verification offer 503”). Verification offer 503 ₁ may include a graphic 5081 associated with a verification institution 110 ₁ and verification fee 506 ₁ associated therewith. Verification offer 503 ₂ may include a graphic 508 ₂ associated with a verification institution 110 ₂ and verification fee 506 ₂ associated therewith. Verification offer 503 ₃ may include a graphic 508 ₃ associated with a verification institution 110 ₃ and verification fee 506 ₃ associated therewith. Each verification offer 503 may be selectable by the payer.

FIG. 5B is a block diagram 550 illustrating one or more screenshots of client computing device 502, according to one or more exemplary embodiments. As illustrated, display 504 of client device 502 may be currently displaying screenshot 555. Screenshot 555 may illustrate an example GUI that may be generated and displayed to the payer upon the payer providing input accepting or rejection a verification offer.

As shown, when a payer provides a select and drag input (e.g., swipe right) the display may update to reveal screenshot 555. The payer may be prompted with one or more options for each verification offer 503. For example, verification offer 503 ₁ may include a graphic 552 ₁ associated with a rejection of the verification offer (e.g. “deny”) and graphic 554 ₁ associated with an approval of the verification offer (e.g. “approve”). Verification offer 503 ₂ may include a graphic 552 ₂ associated with a rejection of the verification offer (e.g. “deny”) and graphic 554 ₂ associated with an approval of the verification offer (e.g. “approve”). Verification offer 503 ₃ may include a graphic 552 ₃ associated with a rejection of the verification offer (e.g. “deny”) and graphic 554 ₃ associated with an approval of the verification offer (e.g. “approve”).

Upon receiving an input via graphic 552 or graphic 554, client device 102 may transmit to verification network 105 a rejection or approval of each verification offer.

It is understood that FIGS. 5A and 5B illustrate an example arrangement, presentation and selection operations of verification offers 503 on display 504 of client device 502. It is understood that verification offers 503 may be arranged and presented in any suitable manner on display 504, and that verification offers 503 may be selected by one or more suitable input operations including operations other than a select and drag input (e.g., swipe right).

FIG. 6 is a block diagram illustrating an exemplary computing environment 600, according to one or more embodiments. Computing environment 600 may include computing system 602 and computing system 652. Computing system 602 may be representative of client device 102. Computing system 652 may be representative of management system 202 or verification network 105.

Computing system 602 may include processor 604, memory 606, storage 608, and network interface 610. In some embodiments, computing system 602 may be coupled to one or more I/O device(s) 612 (e.g., keyboard, mouse, etc.).

Processor 604 may retrieve and execute program code 618 (i.e., programming instructions) stored in memory 606, as well as store and retrieve application data. Processor 604 may be included to be representative of a single processor, multiple processors, a single processor having multiple processing cores, and the like. Network interface 610 may be any type of network communications allowing computing system 602 to communicate externally via computing network 605. For example, network interface 610 may be configured to enable external communication with computing system 652.

Storage 608 may be, for example, a disk storage device. Although shown as a single unit, storage 608 may be a combination of fixed and/or removable storage devices, such as fixed disk drives, removable memory cards, optical storage, network attached storage (NAS), storage area network (SAN), and the like. Storage 608 may include wallet 620. Wallet 620 may be configured to store one or more key pairs associated with a user's blockchain account. Each key pair may include a private key and a corresponding public key.

Memory 606 may include application 614, operating system 616 and program code 618. In some examples, memory 606 may include a geolocation agent (not shown). Program code 618 may be accessed by processor 604 for processing (i.e., executing program instructions). Program code 618 may include, for example, executable instructions for communicating with computing system 652 to display one or more pages of website 662. Application 614 may enable a user of computing system 602 to access a functionality of computing system 652. For example, application 614 may access content managed by computing system 652, such as website 662. The content that is displayed to a user of computing system 602 may be transmitted from computing system 652 to computing system 602, and subsequently processed by application 614 for display through a GUI of computing system 602.

Computing system 652 may include processor 654, memory 656, storage 658, and network interface 660. In some embodiments, computing system 652 may be coupled to one or more I/O device(s) 674. In some embodiments, computing system 652 may be in communication with database 204.

Processor 654 may retrieve and execute program code 666 (i.e., programming instructions) stored in memory 656, as well as store and retrieve application data. Processor 654 is included to be representative of a single processor, multiple processors, a single processor having multiple processing cores, and the like. Network interface 660 may be any type of network communications enabling computing system 652 to communicate externally via computing network 605. For example, network interface 660 may allow computing system 652 to communicate with computer system 602.

Storage 658 may be, for example, a disk storage device. Although shown as a single unit, storage 658 may be a combination of fixed and/or removable storage devices, such as fixed disk drives, removable memory cards, optical storage, network attached storage (NAS), storage area network (SAN), and the like.

Memory 656 may include website 662, operating system 664, program code 666, account handler 668, verification agent 670, and transaction agent 672. Program code 666 may be accessed by processor 654 for processing (i.e., executing program instructions). Program code 666 may include, for example, executable instructions configured to perform steps discussed above in conjunction with FIGS. 3-4 . As an example, processor 654 may access program code 666 to perform operations for verifying a cryptocurrency transaction. Website 662 may be accessed by computing system 602. For example, website 662 may include content accessed by computing system 602 via a web browser or application.

Account handler 668 may be configured to manage one or more accounts associated with one or more users. For example, account handler 668 may communicate with database 204 that stores one or more key pairs 215 (FIG. 2 ). Account handler 668 may generate one or more key pairs upon a user registering with verification network 105. In some embodiments, account handler 668 may generate one or more key pairs stored on computing system 602.

Transaction agent 672 may be configured to manage one or more transactions associated with each account. For example, transaction agent 672 may act as a “middle-man” between computing system 602 and one or more verification institutions 110. In operation, for example, transaction agent 672 may transmit the transaction request to one or more verification institutions 110. Upon receiving input from computing system 602 that corresponds to a selection of a verification offer, transaction agent 672 may transmit the offer acceptance to the respective verification institution 110.

Verification agent 670 may be configured to verify one or more transactions between a payer and a payee. Verification agent 670 may, for example, verify a first signature transmitted from client device 602 to verification network 105 that signals the initiation of the transaction. The first signature may correspond to a first signature needed for a multi-signature transaction. Verification agent 670 may further be configured to verify a second signature transmitted from a verification institution, in response to generation of a verification offer from verification institution 110. The second signature may correspond to a second signature (or additional signature) needed for a multi-signature transaction.

Although not shown in FIG. 6 , each verification institution 110 may also include one or more of the components shown in computing system 652. For example, verification institution 110 may include a processor similar to processor 654, memory similar to memory 656, storage similar to storage 658, a network interface similar to network interface 660 and, in some examples, one or more I/O devices similar to I/O device(s) 674. Similar to memory 656 of computing system 652, the memory of verification institution 110 may also include an operating system similar to operating system 664 and program code similar to program code 666. In contrast to memory 656 of computing system 652, the memory of verification institution 110 may store application 262 (FIG. 2 ) and risk analyzer 264 (FIG. 2 ), and the program code of verification institution 110 may include program instructions relating to application 260 and risk analyzer 264.

. It is understood that aspects of the present disclosure may be implemented in hardware or software or a combination of hardware and software. In one example, aspects of the present disclosure may be implemented as a program product for use with a computer system. The program(s) of the program product define functions of the embodiments (including the methods described herein) and can be contained on a variety of computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory (ROM) devices within a computer, such as compact disk-ROM (CD-ROM) disks readable by a CD-ROM drive, flash memory, ROM chips, or any type of solid-state non-volatile memory) on which information is permanently stored; and (ii) writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive or any type of solid state random-access memory (RAM)) on which alterable information is stored. Such computer-readable storage media, when carrying computer-readable instructions that direct the functions of the present disclosure, are embodiments of the present disclosure.

While the present disclosure has been discussed in terms of certain embodiments, it should be appreciated that the present disclosure is not so limited. The embodiments are explained herein by way of example, and there are numerous modifications, variations and other embodiments that may be employed that would still be within the scope of the present disclosure. 

The invention claimed is:
 1. A system for verifying a blockchain transaction, comprising: one or more verification computing systems; at least one payer computing device; and a verification network, the verification network comprising a computing system having a processor and a memory storing programming instructions; the verification network configured to; receive, over a network, a proposed blockchain transaction generated by the at least one payer computing device, incorporate situational detail data to the proposed blockchain transaction, the situational detail data comprising one or more of transaction information, geolocation data, and merchant data, and broadcast a verification request for the proposed blockchain transaction to the one or more verification computing systems, said verification request including the situational detail data, the one or more verification computing systems configured to: analyze the situational detail data to determine a likelihood of fraud associated with the proposed blockchain transaction, perfect the proposed blockchain transaction to create a perfected blockchain transaction, and broadcast the perfected blockchain transaction directly to a blockchain network, the one or more verification computing systems configured to reverse the perfected blockchain transaction responsive to determining that the proposed blockchain transaction is fraudulent.
 2. The system of claim 1, wherein the proposed blockchain transaction comprises a first signature that is generated using a first private key.
 3. The system of claim 2, wherein the first private key is generated and maintained by the at least one payer computing device.
 4. The system of claim 3, wherein the perfecting the proposed blockchain transaction comprises generating one or more additional signatures using a second private key.
 5. The system of claim 4, wherein the second private key is generated and maintained by the one or more verification computing systems.
 6. The system of claim 1, wherein the transaction information comprises one or more of a time and a value, and the merchant data comprises merchant statistics data.
 7. The system of claim 1, wherein the one or more verification computing systems are further configured to: determine whether the proposed blockchain transaction satisfies one or more pre-agreed threshold parameters, and perfect the proposed blockchain transaction responsive to said analyzing and said determining.
 8. The system of claim 7, wherein, if the one or more verification computing systems determine that the proposed blockchain transaction fails to satisfy the one or more pre-agreed threshold parameters, or in an absence of the one or more pre-agreed threshold parameters, the one or more verification computing systems are further configured to: generate and transmit one or more verification offers to the at least one payer computing device responsive to said verification request; responsive to receiving the one or more verification offers, the at least one payer computing device is further configured to transmit a selection of at least one offer from among the one or more verification offers to the verification network, the selection confirming the proposed blockchain transaction; and upon receiving said selection, the verification network is further configured to broadcast the perfected blockchain transaction to the blockchain network.
 9. The system of claim 8, further comprising a graphical user interface configured to display, on the at least one payer computing device, the one or more verification offers.
 10. The system of claim 8, wherein the one or more verification computing systems are further configured to generate the one or more verification offers based on a risk analysis of the proposed blockchain transaction.
 11. The system of claim 10, wherein the one or more verification offers comprise one or more of an indication of a transaction risk based on the risk analysis, a verification charge based on the risk analysis, and a surge charge based on a volume of verifications requests received by the one or more verification computing systems.
 12. The system of claim 10, wherein the one or more verification computing systems are further configured to assess a risk associated with verifying the proposed blockchain transaction.
 13. The system of claim 12, wherein the risk is based on one or more of a location of the at least one payer computing device, a transaction amount, a frequency of transactions between a payer associated with the at least one payer computing device and a payee, an identity of the payee, a time of the proposed blockchain transaction, and a purchase history of the payer.
 14. The system of claim 8, wherein the verification network further comprises an account handler, a transaction agent, and verification agent, and a database, and wherein: the account handler is configured to generate one or more key pairs, each key pair comprising a public key and a private key, and each key pair associated with a particular user, and to store said one or more key pairs in the database; the transaction agent is configured to perform one or more of: broadcasting the verification request to the one or more verification computing systems, recording the perfected blockchain transaction in the database, and broadcasting the perfected blockchain transaction to the blockchain network; and the verification agent is configured to verify at least one of a first signature and one or more additional signatures.
 15. The system of claim 14, wherein the account handler is further configured to grant access to at least one private key among the one or more key pairs to the one or more verification computing systems; and wherein the one or more verification computing systems are further configured to generate the one or more additional signatures using said at least one private key.
 16. The system of claim 1, wherein the proposed blockchain transaction comprises one or more of a public key associated with the at least one payer computing device, payee address information associated with a payee, a public key associated with the payee, a transaction amount and a specification of two or more additional signatures to perfect the proposed blockchain transaction.
 17. The system of claim 1, wherein the one or more verification computing systems are further configured to: prompt the at least one payer computing device to authenticate with the one or more verification computing systems; confirm an identity of a payer associated with the at least one payer computing device; and verify that an account associated with the payer includes a transaction amount. 